This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
Changes required to be compatible with the pivot extensible discount scripts #1678
+16
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two issues that we had to resolve to use the Shopify CLI's scripts features with pivot
WHY are these changes introduced?
The migrator doesn't properly load with ruby 2.5, I'm not sure why. I get a consistent syntax error:
The package name for discounts was pointing at the checkout package when it actually should have been the discount package, this causes script deploys with
discount-types
to fail.WHAT is this pull request doing?
[1...]
to the equivalentdrop(1)
.drop(1)
is stable over versions since1.8.6
. I would have assumed the same about the array range syntax, but couldn't quite get it to work. I'd like to get this in since it's blocking our local dev environment.How to test your changes?
The fastest way is to use pivot, which will automatically deploy a script for you: https://github.com/Shopify/pivot.
Note that this won't work until https://github.com/Shopify/pivot/pull/12 is merged.
Post-release steps
This is just to unblock our dev team, shouldn't require any special release procedures
Update checklist
I've added a CHANGELOG entry for this PR (if the change is public-facing)Not public facing.